-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(discovery): makes pong send only IP without hostname #2279
Conversation
c7b58f0
to
bec94de
Compare
ffac707
to
875b454
Compare
rskj-core/src/test/java/co/rsk/net/discovery/PeerExplorerTest.java
Outdated
Show resolved
Hide resolved
rskj-core/src/test/java/co/rsk/net/discovery/PeerExplorerTest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job. I don't have any specific remark and I think that what @asoto-iov commented already cover an important part.
I am just wondering if makes sense some more small tests on the places I have commented below. Let me know your opinion, it doesn't prevent the approval.
875b454
to
1354af3
Compare
pipeline:run |
4fb6f63
to
a985e90
Compare
squashme: makes safer test
a985e90
to
2bd1e0d
Compare
Quality Gate passedIssues Measures |
pipeline:run |
1 similar comment
pipeline:run |
As RSK user I want IP addresses (instead of DNS names) to be sent to other peers in response to FIND_NODE peer discovery message
Description
Instead of DNS hostnames a node always sends IP addresses in response to the FIND_NODE peer discovery message
Motivation and Context
As of now, in the peer discovery protocol, when a peer asks for neighbours by sending FIND_NODE message in response it gets a sub list of other discovered peers in a network. Sometimes, instead of IP addresses of remote peers that list might include DNS names resolved via reverse DNS lookup in a context of the peer that returns that response. In some cases this might lead to issues when the reverse DNS resolution happens in different network contexts, for instance, when inside AWS VPC an IP can be resolved to ip-10-10-133-54.us-west-2.compute.internal, but outside that host name would make no sense.
How Has This Been Tested?
Unit test included.
Types of changes
Checklist: